Skip to content

Docs: Add job dispatch and resource tiers documentation#271

Open
erick-GeGe wants to merge 3 commits intomainfrom
docs/job-dispatch
Open

Docs: Add job dispatch and resource tiers documentation#271
erick-GeGe wants to merge 3 commits intomainfrom
docs/job-dispatch

Conversation

@erick-GeGe
Copy link
Copy Markdown
Contributor

Description

Please include a summary of the changes, relevant motivation and context.

Issue

  • Github Issue ID.

Checklist before requesting a review

  • I have performed a self-review of my code.
  • My code follows the style guidelines of this project.
  • I have made corresponding changes to the documentation.
  • New and existing tests pass locally with my changes.
  • If this change is a core feature, I have added thorough tests.
  • If this change affects or depends on the behavior of other estela repositories, I have created pull requests with the relevant changes in the affected repositories. Please, refer to our official documentation.
  • I understand that my pull request may be closed if it becomes obvious or I did not perform all of the steps above.

@erick-GeGe erick-GeGe requested a review from joaquingx March 27, 2026 14:01
Copy link
Copy Markdown
Contributor

@joaquingx joaquingx left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good coverage of the dispatch system, but I think this reads more like internal code notes than documentation. A few suggestions:

Too much implementation detail

  • Things like the Redis lock command (SET spider_jobs_lock 1 NX EX 120), internal function names (_get_cluster_resources(), _dispatch_single_job()), and the "Key Files" table are implementation details that will go stale as code changes. These belong in code comments or docstrings, not in docs.

Suggestion: Simplify to focus on what users need to know (tiers, statuses, config options) and drop the code-level details. The code should document itself.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants